I am looking for the best solution for setting up a very low maintenance reverse proxy for a production website (example.com). The setup is as follows:

• A blog with will be hosted on heroku, and will reside at example.com/blog
• A static info page which will be hosted on S3 and will reside at example.com/signup
• A dynamic content management system, provided and hosted by an external vendor which will respond to requests for any other pages.

The two solutions which come to mind are:

1. Use HAProxy
2. Ask the external vendor to reverse proxy requests for /blog and /signup

The obvious solution would be to use HAProxy, but, if at all possible, I would like to avoid having to setup and maintain another server (especially such a critical one). I came across a company called Snapt which offers hosted HAProxy solutions, but its more geared towards load-balancing than reverse proxying.

Option 2 is a possibility, but gives us very little control over changes and configuration.

I see a lot of sites hosting blogs on /blog so this must be fairly common practice, am I missing an obvious solution?